Skip to content

SREP-1107: Added a new 'managed-scripts' subcommand to osdctl promote#855

Open
Nikokolas3270 wants to merge 1 commit intoopenshift:masterfrom
Nikokolas3270:SREP-1107
Open

SREP-1107: Added a new 'managed-scripts' subcommand to osdctl promote#855
Nikokolas3270 wants to merge 1 commit intoopenshift:masterfrom
Nikokolas3270:SREP-1107

Conversation

@Nikokolas3270
Copy link
Copy Markdown
Contributor

@Nikokolas3270 Nikokolas3270 commented Feb 25, 2026

This also contains the following changes:

  • 'pko' promote subcommand removed as it was no longer applying to any saas file
  • '--osd' and '--hcp' options removed as a there is no service which could be both hcp and osd
  • Now exclusively using 'sigs.k8s.io/kustomize/kyaml' as both a YAML parser & marshaller as 'gopkg.in/yaml.v3' is no longer supported
  • Now interacting with Git repo with 'github.com/go-git/go-git/v6' lib rather than running shell commands
  • Code has been factorized

@openshift-ci-robot openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Feb 25, 2026
@openshift-ci-robot
Copy link
Copy Markdown

openshift-ci-robot commented Feb 25, 2026

@Nikokolas3270: This pull request references SREP-1107 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the story to target the "4.22.0" version, but no target version was set.

Details

In response to this:

This also contains the following changes:

  • 'pko' promote subcommand removed as it was no longer applying to any saas file
  • '--osd' and '--hcp' options removed as a there is no service which could be both hcp and osd
  • Now exclusively using 'sigs.k8s.io/kustomize/kyaml' as both a YAML parser & marshaller as 'gopkg.in/yaml.v3' is no longer supported
  • Now interacting with Git repo with 'github.com/go-git/go-git/v6' lib rather than running shell commands
  • Code has been factorized

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

@coderabbitai
Copy link
Copy Markdown

coderabbitai bot commented Feb 25, 2026

Walkthrough

Registry-driven service promotion replaces prior app-interface/git-centric promotion flows: new utilities for local repo handling, service model and registry, and go-git-based repo introspection were added; PKO and legacy app-interface/service_repo/pathutil code and tests were removed; a new managedscripts promote subcommand and test suite were introduced.

Changes

Cohort / File(s) Summary
Command wiring
cmd/promote/cmd.go
Replaced pko subcommand with managedscripts subcommand registration.
ManagedScripts command & tests
cmd/promote/managedscripts/managed_scripts.go, cmd/promote/managedscripts/managed_scripts_test.go
Added managedscripts promote command and corresponding Ginkgo test suite; command wires promotion callbacks and flags (--gitHash, --appInterfaceDir).
PKO removal
cmd/promote/pko/pko.go
Removed the PKO/package promote command and its promotion logic.
Dynatrace refactor & tests
cmd/promote/dynatrace/dynatrace.go, cmd/promote/dynatrace/dt_utils.go, cmd/promote/dynatrace/utils_test.go
Switched Dynatrace flow to registry-driven lookup and kyaml traversal, converted command to RunE, renamed GeModulesNames→GetModulesNames, removed local SAAS-file enumeration/parsing helpers.
SaaS refactor & tests
cmd/promote/saas/saas.go, (removed) cmd/promote/saas/utils.go, (removed) cmd/promote/saas/utils_test.go, cmd/promote/saas/saas_test.go
Removed legacy saas utilities; added service-file path validation, promoteCallbacks, e2e helpers, flag/validation changes (--serviceId, --hotfix, --appInterfaceDir), and updated promote flow to use ServicesRegistry; added new Ginkgo tests.
Removed pathutil
cmd/promote/pathutil/pathutil.go, cmd/promote/pathutil/pathutil_test.go
Deleted path derivation implementation and its tests.
Removed git/app-interface & service_repo
cmd/promote/git/app_interface.go, cmd/promote/git/app_interface_test.go, cmd/promote/git/service_repo.go, cmd/promote/git/service_repo_test.go
Deleted previous app-interface and service-repo git abstractions and associated tests.
New utils: app-interface clone
cmd/promote/utils/app_interface_clone.go, cmd/promote/utils/app_interface_clone_test.go
Added AppInterfaceClone type and FindAppInterfaceClone for validating local app-interface clones, branch checkout and commit helpers; included tests.
New utils: git repo (go-git)
cmd/promote/utils/git_repo.go
Added Repo wrapper using go-git: clone/mirror, ResolveHash, GetHeadHash, FormattedLog, Cleanup and helpers for commit-log formatting.
New utils: service model & registry
cmd/promote/utils/service.go, cmd/promote/utils/services_registry.go, cmd/promote/utils/services_registry_test.go
Added Service/Application/CodeComponent models, PromoteCallbacks interface and DefaultPromoteCallbacks, Service.Promote implementation, and ServicesRegistry for discovering/loading services; added tests.
Test infra & suites
cmd/promote/utils/test_tools.go, cmd/promote/utils/*_test.go, cmd/promote/utils/service_test.go, cmd/promote/saas/saas_test.go, cmd/promote/managedscripts/managed_scripts_test.go
Introduced comprehensive test tooling, templates, and Ginkgo/Gomega suites covering new utils, registry, service promotion, AppInterfaceClone and managedscripts scenarios.
Docs updated/added
docs/README.md, docs/osdctl_promote.md, docs/osdctl_promote_managedscripts.md, docs/osdctl_promote_saas.md, docs/osdctl_promote_dynatrace.md
Replaced package command docs with managedscripts, updated saas/dynatrace flag docs and examples to reflect new flags and behaviors.
Dependencies
go.mod
Added github.com/go-git/go-git/v5 and related indirect dependencies required by new go-git usage.

Estimated code review effort

🎯 5 (Critical) | ⏱️ ~120 minutes

🚥 Pre-merge checks | ✅ 4 | ❌ 1

❌ Failed checks (1 warning)

Check name Status Explanation Resolution
Test Structure And Quality ⚠️ Warning Pull request deletes 1,777 lines of tests while adding 824 lines of untested production code across five new files with no corresponding test files. Create comprehensive test files for all new utilities following table-driven test patterns with proper setup/cleanup, error paths, edge cases, and meaningful assertions.
✅ Passed checks (4 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The title clearly and accurately summarizes the main change: adding a new 'managed-scripts' subcommand to the promote command.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Stable And Deterministic Test Names ✅ Passed No dynamic test names containing generated IDs, timestamps, pod names, UUIDs, or other non-deterministic values were found in any test files. All test cases use static, stable test descriptions.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.

✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests

Comment @coderabbitai help to get the list of available commands and usage tips.

@openshift-ci
Copy link
Copy Markdown
Contributor

openshift-ci bot commented Feb 25, 2026

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: Nikokolas3270

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Details Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@openshift-ci openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Feb 25, 2026
@Nikokolas3270 Nikokolas3270 marked this pull request as draft February 25, 2026 09:20
@openshift-ci openshift-ci bot added the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Feb 25, 2026
@openshift-ci-robot
Copy link
Copy Markdown

openshift-ci-robot commented Feb 25, 2026

@Nikokolas3270: This pull request references SREP-1107 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the story to target the "4.22.0" version, but no target version was set.

Details

In response to this:

This also contains the following changes:

  • 'pko' promote subcommand removed as it was no longer applying to any saas file
  • '--osd' and '--hcp' options removed as a there is no service which could be both hcp and osd
  • Now exclusively using 'sigs.k8s.io/kustomize/kyaml' as both a YAML parser & marshaller as 'gopkg.in/yaml.v3' is no longer supported
  • Now interacting with Git repo with 'github.com/go-git/go-git/v6' lib rather than running shell commands
  • Code has been factorized

Summary by CodeRabbit

Release Notes

  • New Features

  • Added new osdctl promote managedscripts command for promoting managed-scripts repository commits

  • Improvements

  • Refactored promotion system to use registry-based service discovery for more reliable configuration lookup

  • Enhanced commit messages with monitoring links and test log references

  • Improved error handling and control flow across promotion workflows

  • Removed

  • Removed osdctl promote package command

  • Consolidated OSD/HCP flag behavior into unified promotion flow

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

Copy link
Copy Markdown

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 14

Caution

Some comments are outside the diff and can’t be posted inline due to platform limitations.

⚠️ Outside diff range comments (3)
cmd/promote/dynatrace/dt_utils.go (2)

175-178: ⚠️ Potential issue | 🟠 Major

Return immediately when opening the file fails.

The current flow logs the error and continues, which can pass an invalid file handle into downstream processing.

Proposed fix
 	file, err := Open(filename)
 	if err != nil {
-		fmt.Println(err)
+		return fmt.Errorf("failed to open file '%s': %w", filename, err)
 	}
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.

In `@cmd/promote/dynatrace/dt_utils.go` around lines 175 - 178, The Open(filename)
call currently prints the error and continues, which can pass an invalid file
handle into downstream code; update the error handling at the Open(...) site so
that on err you return the error (or otherwise abort the function) instead of
just fmt.Println(err). Locate the Open(filename) invocation in dt_utils.go and
modify the surrounding function to propagate the error (or call return)
immediately when err != nil, ensuring downstream code does not receive a
nil/invalid file handle.

142-153: ⚠️ Potential issue | 🟠 Major

Propagate os.ReadDir failures instead of discarding them.

Read errors are currently ignored at multiple levels, so the promotion can incorrectly continue as if files were scanned successfully.

Proposed fix
-	items, _ := os.ReadDir(dir)
+	items, err := os.ReadDir(dir)
+	if err != nil {
+		return "", fmt.Errorf("failed to read directory '%s': %w", dir, err)
+	}
...
-			subitems, _ := os.ReadDir(subDir)
+			subitems, err := os.ReadDir(subDir)
+			if err != nil {
+				return "", fmt.Errorf("failed to read directory '%s': %w", subDir, err)
+			}
...
-					subitems2, _ := os.ReadDir(subDir2)
+					subitems2, err := os.ReadDir(subDir2)
+					if err != nil {
+						return "", fmt.Errorf("failed to read directory '%s': %w", subDir2, err)
+					}
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.

In `@cmd/promote/dynatrace/dt_utils.go` around lines 142 - 153, The os.ReadDir
calls in the nested directory walk (the reads that populate items, subitems and
subitems2) currently ignore their returned errors; change each call to capture
the error (e.g., items, err := os.ReadDir(dir)) and propagate it instead of
discarding it—return the error (or wrap and return) from the enclosing function
(the directory-walking function in dt_utils.go) so failures stop the promotion;
do the same for subitems and subitems2 reads and adjust calling code to handle
the returned error.
cmd/promote/dynatrace/dynatrace.go (1)

73-74: ⚠️ Potential issue | 🟠 Major

Don’t ignore list errors before successful exit.

Both list branches discard the returned error and then exit with success, which can hide real failures from users and automation.

Proposed fix
-					_ = listDynatraceModuleNames(dynatraceConfig)
-					os.Exit(0)
+					if err := listDynatraceModuleNames(dynatraceConfig); err != nil {
+						return fmt.Errorf("failed to list dynatrace modules: %w", err)
+					}
+					return nil
...
-					_ = listServiceIds(servicesRegistry)
-					os.Exit(0)
+					if err := listServiceIds(servicesRegistry); err != nil {
+						return fmt.Errorf("failed to list dynatrace components: %w", err)
+					}
+					return nil

Also applies to: 117-118

🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.

In `@cmd/promote/dynatrace/dynatrace.go` around lines 73 - 74, The calls to
listDynatraceModuleNames currently discard the returned error and then call
os.Exit(0); change both call sites to capture the error (e.g., err :=
listDynatraceModuleNames(dynatraceConfig)), check if err != nil, print or log
the error to stderr (or use the existing logger) and call os.Exit(1); if no
error, then exit with success. This ensures failures from
listDynatraceModuleNames are surfaced instead of being silently ignored.
🧹 Nitpick comments (5)
cmd/promote/dynatrace/dt_utils.go (1)

108-124: Reset module caches in GetModulesNames before repopulating.

ModulesSlice and ModulesFilesMap are package globals and currently accumulate across repeated calls.

Proposed fix
 func GetModulesNames(baseDir, dir string) ([]string, error) {
+	ModulesSlice = ModulesSlice[:0]
+	ModulesFilesMap = map[string]string{}
+
 	dirGlob := filepath.Join(baseDir, dir)
 	filepaths, err := os.ReadDir(dirGlob)
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.

In `@cmd/promote/dynatrace/dt_utils.go` around lines 108 - 124, GetModulesNames
currently appends to package globals ModulesSlice and ModulesFilesMap on each
call; modify GetModulesNames to reset/clear ModulesSlice and reinitialize or
clear ModulesFilesMap at the start of the function (before reading dir entries)
so repeated calls don't accumulate stale data; locate the function
GetModulesNames and add logic to set ModulesSlice = nil (or empty slice) and
ModulesFilesMap = make(map[string]string) (or clear existing entries) before
populating them.
cmd/promote/utils/service.go (4)

42-44: Inconsistent receiver name on yamlDoc.

GetFilePath (line 38) and Save (line 46) use d, but GetName uses s. Use a consistent receiver name across all methods of the same type.

Proposed fix
-func (s *yamlDoc) GetName() string {
-	return s.name
+func (d *yamlDoc) GetName() string {
+	return d.name
 }
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.

In `@cmd/promote/utils/service.go` around lines 42 - 44, The GetName method for
type yamlDoc uses an inconsistent receiver name `s`; change its receiver to `d`
to match the other methods on yamlDoc (e.g., GetFilePath and Save) so all
methods use the same receiver identifier; update the method signature for
GetName to use `d` and keep the body returning d.name.

413-419: Nit: unconventional blank line in error handling.

The blank line between the call on line 414 and the if err != nil on line 416 breaks the standard Go error-handling idiom. Consider removing it for consistency.

Proposed fix
 	if newHash == "" {
 		newHash, err = repo.GetHeadHash()
-
 		if err != nil {
 			return err
 		}
 	}
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.

In `@cmd/promote/utils/service.go` around lines 413 - 419, Remove the extra blank
line in the error handling after calling repo.GetHeadHash so the idiomatic Go
pattern is preserved; specifically, in the block that assigns newHash (the call
to repo.GetHeadHash) and the subsequent if err != nil block, bring the if
directly under the call (no blank line) to keep the standard newHash, err :=
repo.GetHeadHash / if err != nil style used elsewhere.

296-330: Partial failure leaves committed state in the local branch.

Each resourceTemplatePromotion.promote call saves the YAML and commits independently (lines 307, 318). If a later promotion in the loop (line 428) fails, earlier promotions are already committed to the local branch. This is likely acceptable since the user must manually push, but consider documenting this behavior or logging a warning when a partial failure occurs so users know what's been committed.

🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.

In `@cmd/promote/utils/service.go` around lines 296 - 330, The promote function
(resourceTemplatePromotion.promote) commits each resource independently (uses
callbacks.SetTargetHash, service.Save, service.appInterfaceClone.Commit) which
can leave the local branch partially committed if a later promotion fails;
update the caller that loops over promotions (the code that invokes
resourceTemplatePromotion.promote) to track which promotions succeeded and, on
any subsequent error, emit a clear warning/log that lists the committed resource
relPaths and informs the user that the local branch contains partial commits
requiring manual push/revert; alternatively expose a boolean or error type from
promote indicating "committed" so the caller can build that list before logging
the warning.

21-21: Export the yamlDoc type to match its exported function.

ReadYamlDocFromFile is exported and used externally (e.g., cmd/promote/saas/saas.go:118), but it returns *yamlDoc, which is unexported. This violates Go conventions — external callers cannot declare variables of this type. Export yamlDoc as YamlDoc (or use the lowercase-exported pattern if intentional, but document it).

Additionally, the receiver names for yamlDoc methods are inconsistent: GetFilePath() and Save() use receiver d, while GetName() (line 42) uses receiver s. Standardize on a single receiver name like d.

🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.

In `@cmd/promote/utils/service.go` at line 21, The exported function
ReadYamlDocFromFile returns an unexported type yamlDoc which prevents external
callers from using its value; rename the type to exported YamlDoc (or change the
function to return an exported interface) and update all references accordingly
(including ReadYamlDocFromFile's return type and any uses in
cmd/promote/saas/saas.go). Also standardize method receiver names on that type:
change the GetName receiver from 's' to 'd' to match GetFilePath and Save so all
methods on yamlDoc/YamlDoc use a consistent receiver (d). Ensure you update any
imports/usages and tests to the new exported type name.
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.

Inline comments:
In `@cmd/promote/managedscripts/managed_scripts.go`:
- Around line 30-32: The FilterTargets method currently hardcodes
prodNamespaceRef when calling utils.FilterTargetsContainingNamespaceRef, so the
configured --namespaceRef value is ignored; update
promoteCallbacks.FilterTargets to pass the instance/configured namespace
reference (e.g., c.namespaceRef or the field that holds the CLI flag) into
utils.FilterTargetsContainingNamespaceRef instead of prodNamespaceRef, ensuring
the same change is applied where else prodNamespaceRef is used for target
selection so the runtime flag actually influences filtering.

In `@cmd/promote/saas/saas.go`:
- Line 234: Update the CLI help/example string to use the canonical flag
--serviceId instead of the legacy alias --serviceName: locate the usage text
that currently reads `osdctl promote saas --serviceName <service> --gitHash
<git-hash>` (in the promote command's help/usage output) and replace
`--serviceName` with `--serviceId`; ensure any adjacent help text or examples
referencing the legacy alias are also updated so the example consistently shows
`--serviceId <service>` with `--gitHash <git-hash>`.
- Around line 271-274: Add a fail-fast required check for ops.serviceId before
calling servicesRegistry.GetService to give a clearer error for promote mode:
validate that ops.serviceId is non-empty (e.g., at the start of the promote
handler or before the GetService call), and return a descriptive error if it's
empty (mentioning that --serviceId is required in promote mode). Update the code
path where servicesRegistry.GetService(ops.serviceId) is invoked (reference
ops.serviceId and the promote handler function) to perform this explicit check
and only call GetService when the value is present.
- Around line 38-43: The current logic returns the original filePath when
deploy.yaml is missing, which can register a directory as a service; change the
code to only return valid regular file paths: after checking subFilePath, also
verify that filePath itself is a regular file (use os.Stat(filePath) and
fileInfo.Mode().IsRegular()) before returning it, and if it's a directory or not
a regular file return an empty string (or an error sentinel) so the caller can
skip this SaaS entry; adjust callers of this helper to treat empty string as
"skip invalid entry".

In `@cmd/promote/utils/git_repo.go`:
- Around line 54-89: The code pre-marks commonAncestorCommit.Hash in
visitedHashes before traversal which allows walks that never actually reach
commonAncestorHash to succeed silently; modify the traversal in the function
containing queue, visitedHashes, commit.IsAncestor and the final sb.WriteString
branch so that you either do not pre-populate visitedHashes with
commonAncestorCommit.Hash or (preferably) add a post-traversal check that
verifies visitedHashes contains commonAncestorHash (or that you visited it
during traversal) and return an explicit error if it was not reached; use the
symbols visitedHashes, commonAncestorCommit / commonAncestorHash, queue,
commit.IsAncestor and the final return path to locate where to add the check.

In `@cmd/promote/utils/service.go`:
- Around line 212-229: The function FilterTargetsContainingNamespaceRef
currently uses strings.Contains(visitedNamespaceRef, namespaceRef) which allows
substring matches; change the check to a precise match (e.g., verify the path
ends with the expected segment or exact identifier) by replacing the contains
logic with a more strict comparison such as using strings.HasSuffix or parsing
visitedNamespaceRef into path segments and comparing the final segment to
namespaceRef (operate on visitedNamespaceRef and namespaceRef variables inside
FilterTargetsContainingNamespaceRef so only exact/segment matches are
considered).
- Around line 141-146: The code reads appRelFilePath from
yamlDoc.rootNode.GetString and directly uses
filepath.Join(appInterfaceClone.GetPath(), "data", appRelFilePath) before
calling readApplicationFromFile; sanitize appRelFilePath by running
filepath.Clean, reject absolute paths or any path that resolves outside the
intended base (e.g. contains ".." segments that escape the
appInterfaceClone.GetPath()/data directory), and construct the final path by
joining the cleaned relative path to appInterfaceClone.GetPath()/data then
verifying the resulting path has the base directory as a prefix before calling
readApplicationFromFile.
- Around line 389-394: Iterate deterministically over oldHashToTargetNodes by
collecting its keys into a slice, sorting that slice (using sort.Strings), and
then building resourceTemplatePromotions in the sorted order (instead of ranging
the map directly); update the import block to include "sort". Ensure the same
symbols are used: oldHashToTargetNodes, resourceTemplatePromotions,
resourceTemplatePromotion, and that downstream code that calls promote will now
see a stable commit order.

In `@cmd/promote/utils/services_registry.go`:
- Around line 19-33: The constructor NewServicesRegistry should guard against
nil inputs to avoid panics: at the start of the function check if
appInterfaceClone is nil and if so return a descriptive error (do not call
appInterfaceClone.GetPath()); also check if validateServiceFilePathCallback is
nil and return a descriptive error before invoking it later; update
callers/tests if necessary to pass non-nil values or to handle the returned
error from NewServicesRegistry.
- Around line 36-37: The code silently overwrites existing entries in the
serviceIdToFilePath map (variable serviceId) when scanning files; change the
insertion logic to fail fast on duplicates by checking if serviceId already
exists in serviceIdToFilePath and returning/propagating an error (or logging and
exiting) that includes the conflicting serviceId and both file paths (existing
value and serviceFilePath) so callers of the scanning function can handle the
failure instead of allowing silent overwrite.

In `@docs/osdctl_promote_managedscripts.md`:
- Around line 5-39: Add language identifiers to all fenced code blocks in
docs/osdctl_promote_managedscripts.md to satisfy MD040: mark the command usage
block as "text" (or "bash" if preferred), the example block as "bash", and both
options blocks (Options and Options inherited from parent commands) as "text".
Update the fences surrounding the snippets that contain "osdctl promote
managedscripts [flags]", the example starting with "# Promote managed-scripts
repo", the options list beginning with "--appInterfaceDir", and the inherited
options list beginning with "--as" to include the appropriate language tags.

In `@docs/osdctl_promote_saas.md`:
- Around line 22-30: The fenced code block showing CLI flags in the saas
promotion docs lacks a language identifier which triggers markdownlint MD040;
update the triple-backtick opening fence to include a language (e.g., ```text)
for the block containing the lines starting with "--appInterfaceDir" and ending
with "--serviceId" so the block is treated as plain text and the linter warning
is resolved.
- Line 17: The example for the CLI invocation uses the deprecated alias flag
--serviceName; update the example for the command osdctl promote saas to use the
canonical flag --serviceId instead (replace the --serviceName token with
--serviceId in the example line) so the documentation shows the current,
supported flag.

In `@docs/README.md`:
- Around line 3938-3940: Add a language identifier to the fenced code block that
contains the line "osdctl promote managedscripts [flags]" so markdownlint MD040
is satisfied; modify the opening fence from ``` to ```text (or ```bash) around
the block in README.md so it becomes ```text followed by the command and closing
``` to preserve formatting.

---

Outside diff comments:
In `@cmd/promote/dynatrace/dt_utils.go`:
- Around line 175-178: The Open(filename) call currently prints the error and
continues, which can pass an invalid file handle into downstream code; update
the error handling at the Open(...) site so that on err you return the error (or
otherwise abort the function) instead of just fmt.Println(err). Locate the
Open(filename) invocation in dt_utils.go and modify the surrounding function to
propagate the error (or call return) immediately when err != nil, ensuring
downstream code does not receive a nil/invalid file handle.
- Around line 142-153: The os.ReadDir calls in the nested directory walk (the
reads that populate items, subitems and subitems2) currently ignore their
returned errors; change each call to capture the error (e.g., items, err :=
os.ReadDir(dir)) and propagate it instead of discarding it—return the error (or
wrap and return) from the enclosing function (the directory-walking function in
dt_utils.go) so failures stop the promotion; do the same for subitems and
subitems2 reads and adjust calling code to handle the returned error.

In `@cmd/promote/dynatrace/dynatrace.go`:
- Around line 73-74: The calls to listDynatraceModuleNames currently discard the
returned error and then call os.Exit(0); change both call sites to capture the
error (e.g., err := listDynatraceModuleNames(dynatraceConfig)), check if err !=
nil, print or log the error to stderr (or use the existing logger) and call
os.Exit(1); if no error, then exit with success. This ensures failures from
listDynatraceModuleNames are surfaced instead of being silently ignored.

---

Nitpick comments:
In `@cmd/promote/dynatrace/dt_utils.go`:
- Around line 108-124: GetModulesNames currently appends to package globals
ModulesSlice and ModulesFilesMap on each call; modify GetModulesNames to
reset/clear ModulesSlice and reinitialize or clear ModulesFilesMap at the start
of the function (before reading dir entries) so repeated calls don't accumulate
stale data; locate the function GetModulesNames and add logic to set
ModulesSlice = nil (or empty slice) and ModulesFilesMap =
make(map[string]string) (or clear existing entries) before populating them.

In `@cmd/promote/utils/service.go`:
- Around line 42-44: The GetName method for type yamlDoc uses an inconsistent
receiver name `s`; change its receiver to `d` to match the other methods on
yamlDoc (e.g., GetFilePath and Save) so all methods use the same receiver
identifier; update the method signature for GetName to use `d` and keep the body
returning d.name.
- Around line 413-419: Remove the extra blank line in the error handling after
calling repo.GetHeadHash so the idiomatic Go pattern is preserved; specifically,
in the block that assigns newHash (the call to repo.GetHeadHash) and the
subsequent if err != nil block, bring the if directly under the call (no blank
line) to keep the standard newHash, err := repo.GetHeadHash / if err != nil
style used elsewhere.
- Around line 296-330: The promote function (resourceTemplatePromotion.promote)
commits each resource independently (uses callbacks.SetTargetHash, service.Save,
service.appInterfaceClone.Commit) which can leave the local branch partially
committed if a later promotion fails; update the caller that loops over
promotions (the code that invokes resourceTemplatePromotion.promote) to track
which promotions succeeded and, on any subsequent error, emit a clear
warning/log that lists the committed resource relPaths and informs the user that
the local branch contains partial commits requiring manual push/revert;
alternatively expose a boolean or error type from promote indicating "committed"
so the caller can build that list before logging the warning.
- Line 21: The exported function ReadYamlDocFromFile returns an unexported type
yamlDoc which prevents external callers from using its value; rename the type to
exported YamlDoc (or change the function to return an exported interface) and
update all references accordingly (including ReadYamlDocFromFile's return type
and any uses in cmd/promote/saas/saas.go). Also standardize method receiver
names on that type: change the GetName receiver from 's' to 'd' to match
GetFilePath and Save so all methods on yamlDoc/YamlDoc use a consistent receiver
(d). Ensure you update any imports/usages and tests to the new exported type
name.

ℹ️ Review info

Configuration used: Repository: openshift/coderabbit/.coderabbit.yaml

Review profile: CHILL

Plan: Pro

Cache: Disabled due to data retention organization setting

Knowledge base: Disabled due to data retention organization setting

📥 Commits

Reviewing files that changed from the base of the PR and between ba2de78 and 90a34b6.

⛔ Files ignored due to path filters (1)
  • go.sum is excluded by !**/*.sum
📒 Files selected for processing (23)
  • cmd/promote/cmd.go
  • cmd/promote/dynatrace/dt_utils.go
  • cmd/promote/dynatrace/dynatrace.go
  • cmd/promote/dynatrace/utils_test.go
  • cmd/promote/git/app_interface.go
  • cmd/promote/git/app_interface_test.go
  • cmd/promote/git/service_repo.go
  • cmd/promote/git/service_repo_test.go
  • cmd/promote/managedscripts/managed_scripts.go
  • cmd/promote/pathutil/pathutil_test.go
  • cmd/promote/pko/pko.go
  • cmd/promote/saas/saas.go
  • cmd/promote/saas/utils.go
  • cmd/promote/saas/utils_test.go
  • cmd/promote/utils/app_interface_clone.go
  • cmd/promote/utils/git_repo.go
  • cmd/promote/utils/service.go
  • cmd/promote/utils/services_registry.go
  • docs/README.md
  • docs/osdctl_promote.md
  • docs/osdctl_promote_managedscripts.md
  • docs/osdctl_promote_saas.md
  • go.mod
💤 Files with no reviewable changes (8)
  • cmd/promote/pathutil/pathutil_test.go
  • cmd/promote/pko/pko.go
  • cmd/promote/saas/utils.go
  • cmd/promote/git/app_interface_test.go
  • cmd/promote/git/service_repo.go
  • cmd/promote/git/app_interface.go
  • cmd/promote/git/service_repo_test.go
  • cmd/promote/saas/utils_test.go

Copy link
Copy Markdown
Member

@MateSaary MateSaary left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The promotion command's code finally looks much better 😄 Added a few comments, aside from that;

  • There was decent test coverage for the command before which is now gone; would be nice to have it back but can also be done as a follow-up, we do already have a card for this in backlog: https://issues.redhat.com/browse/SREP-1278

  • it looks like pathutil/pathutil.go isn't being used anywhere now, so we could remove that orphaned code with this PR too

I tried to go through the coderabbit suggestions as well and commented/reacted to them based on whether or not they make sense 😄

@Nikokolas3270
Copy link
Copy Markdown
Contributor Author

Nikokolas3270 commented Feb 26, 2026

The promotion command's code finally looks much better 😄 Added a few comments, aside from that;

Thanks :)

  • There was decent test coverage for the command before which is now gone; would be nice to have it back but can also be done as a follow-up, we do already have a card for this in backlog: https://issues.redhat.com/browse/SREP-1278
  • it looks like pathutil/pathutil.go isn't being used anywhere now, so we could remove that orphaned code with this PR too

True, I am still working on the unit-tests, no worries. I just wanted to have people a first look on that finally quite big change.

I tried to go through the coderabbit suggestions as well and commented/reacted to them based on whether or not they make sense 😄

Thanks! I will TAL as well

@Nikokolas3270 Nikokolas3270 marked this pull request as ready for review March 27, 2026 17:56
@openshift-ci openshift-ci bot removed the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Mar 27, 2026
@openshift-ci openshift-ci bot requested review from petrkotas and typeid March 27, 2026 17:57
@openshift-ci-robot
Copy link
Copy Markdown

openshift-ci-robot commented Mar 27, 2026

@Nikokolas3270: This pull request references SREP-1107 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the story to target the "4.22.0" version, but no target version was set.

Details

In response to this:

This also contains the following changes:

  • 'pko' promote subcommand removed as it was no longer applying to any saas file
  • '--osd' and '--hcp' options removed as a there is no service which could be both hcp and osd
  • Now exclusively using 'sigs.k8s.io/kustomize/kyaml' as both a YAML parser & marshaller as 'gopkg.in/yaml.v3' is no longer supported
  • Now interacting with Git repo with 'github.com/go-git/go-git/v6' lib rather than running shell commands
  • Code has been factorized

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

Copy link
Copy Markdown

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 3

Caution

Some comments are outside the diff and can’t be posted inline due to platform limitations.

⚠️ Outside diff range comments (1)
cmd/promote/dynatrace/dt_utils.go (1)

137-166: ⚠️ Potential issue | 🟡 Minor

Errors from os.ReadDir are silently ignored.

Lines 140 and 145 discard errors from os.ReadDir. This could mask permission issues or missing directories, leading to confusing behavior.

🛡️ Proposed fix
 func updatePromotionGitHash(module string, dir string, promotionGitHash string) (string, error) {
 
 	fmt.Printf("Iterating over directory : %s", dir)
-	items, _ := os.ReadDir(dir)
+	items, err := os.ReadDir(dir)
+	if err != nil {
+		return "", fmt.Errorf("failed to read directory '%s': %v", dir, err)
+	}
 	for _, item := range items {
 		fmt.Println("Production tenant: ", item.Name())
 		if item.IsDir() {
 			subDir := filepath.Join(dir, item.Name())
-			subitems, _ := os.ReadDir(subDir)
+			subitems, err := os.ReadDir(subDir)
+			if err != nil {
+				return "", fmt.Errorf("failed to read subdirectory '%s': %v", subDir, err)
+			}
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.

In `@cmd/promote/dynatrace/dt_utils.go` around lines 137 - 166, The function
updatePromotionGitHash currently ignores errors returned by os.ReadDir (when
listing dir, subDir, and subDir2), which can hide permission or
missing-directory problems; update each os.ReadDir call to capture its error,
check it, and return a wrapped error (including the path and original error)
instead of proceeding silently so callers can fail fast—apply this to the
top-level items, subitems and subitems2 reads in updatePromotionGitHash and
propagate or return errors from updateFileContent as appropriate.
♻️ Duplicate comments (1)
cmd/promote/dynatrace/dynatrace.go (1)

126-131: ⚠️ Potential issue | 🟠 Major

Return the promotion error instead of exiting the process.

os.Exit(1) bypasses Cobra's RunE error path and skips deferred cleanup/tests.

🔧 Proposed fix
-					err = service.Promote(&utils.DefaultPromoteCallbacks{Service: service}, ops.gitHash)
-
-					if err != nil {
-						fmt.Printf("Error while promoting service: %v\n", err)
-						os.Exit(1)
-					}
+					if err := service.Promote(&utils.DefaultPromoteCallbacks{Service: service}, ops.gitHash); err != nil {
+						return fmt.Errorf("error while promoting service: %w", err)
+					}
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.

In `@cmd/promote/dynatrace/dynatrace.go` around lines 126 - 131, The code
currently calls fmt.Printf and os.Exit(1) after service.Promote fails, which
prevents Cobra's RunE error handling and deferred cleanup; change the block in
the function that calls service.Promote(&utils.DefaultPromoteCallbacks{Service:
service}, ops.gitHash) to return the error (or a wrapped error with context)
instead of printing and exiting so the caller/RunE can handle it and deferred
cleanup runs; specifically remove fmt.Printf/os.Exit and return err (or
fmt.Errorf("promote failed: %w", err)) from the surrounding command handler.
🧹 Nitpick comments (3)
cmd/promote/utils/git_repo.go (1)

70-75: Minor: Missing space in warning message.

Line 73 has "Warning:Failed" - should be "Warning: Failed" for consistency with line 40.

✏️ Fix formatting
 func (r *Repo) Cleanup() {
 	err := os.RemoveAll(r.clonePath)
 	if err != nil {
-		fmt.Printf("Warning:Failed to remove clone directory '%s': %v", r.clonePath, err)
+		fmt.Printf("Warning: Failed to remove clone directory '%s': %v", r.clonePath, err)
 	}
 }
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.

In `@cmd/promote/utils/git_repo.go` around lines 70 - 75, The warning string in
Repo.Cleanup uses "Warning:Failed" without a space; update the fmt.Printf call
inside Cleanup (function Repo.Cleanup) to insert a space after the colon (i.e.,
"Warning: Failed to remove clone directory '%s': %v") so the message matches the
formatting used elsewhere (referencing r.clonePath and the fmt.Printf call).
cmd/promote/dynatrace/dt_utils.go (1)

25-28: Package-level mutable state can cause test pollution.

ModulesSlice and ModulesFilesMap are package-level variables that GetModulesNames appends to. This can cause issues if tests run in parallel or if the function is called multiple times.

Consider returning fresh slices/maps instead of mutating package-level state, or clearing them at the start of GetModulesNames.

Also applies to: 106-123

🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.

In `@cmd/promote/dynatrace/dt_utils.go` around lines 25 - 28, ModulesSlice and
ModulesFilesMap are package-level mutable variables that GetModulesNames appends
to, causing test pollution; change GetModulesNames to use and return fresh local
variables (e.g., local modulesSlice []string and modulesFilesMap
map[string]string) instead of appending to the package-level
ModulesSlice/ModulesFilesMap, and update callers to accept the returned
slice/map, or alternatively clear ModulesSlice and ModulesFilesMap at the start
of GetModulesNames before use; apply the same local/clear fix to the other
similar code block referenced around lines 106-123 (same function or helper) so
no package-level mutation persists across calls/tests.
cmd/promote/utils/app_interface_clone.go (1)

110-128: Consider detecting the default branch dynamically instead of hardcoding master.

The function assumes master is the default branch, which is correct for osdctl. However, many repositories now use main as the default. For robustness, consider detecting the default branch dynamically or making it configurable, so the function doesn't fail if used with repositories that have adopted main.

♻️ Suggested approach
-func (a *AppInterfaceClone) CheckoutNewBranch(branchName string) error {
-	if err := a.workTree.Checkout(&git.CheckoutOptions{Branch: plumbing.NewBranchReferenceName("master")}); err != nil {
-		return fmt.Errorf("failed to checkout master branch in '%s': %v", a.path, err)
+func (a *AppInterfaceClone) CheckoutNewBranch(branchName string, baseBranch string) error {
+	if baseBranch == "" {
+		baseBranch = "master"
+	}
+	if err := a.workTree.Checkout(&git.CheckoutOptions{Branch: plumbing.NewBranchReferenceName(baseBranch)}); err != nil {
+		return fmt.Errorf("failed to checkout %s branch in '%s': %v", baseBranch, a.path, err)
 	}
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.

In `@cmd/promote/utils/app_interface_clone.go` around lines 110 - 128,
CheckoutNewBranch currently hardcodes "master"; change it to detect the
repository's current/default branch instead and use that for the initial
checkout. In CheckoutNewBranch use repo.Head() (or resolve
"refs/remotes/origin/HEAD" if you need remote default) to obtain the default
branch reference name and pass that into workTree.Checkout instead of
plumbing.NewBranchReferenceName("master"), falling back to "master" or "main"
only if detection fails; keep existing logic for branchReference creation,
repo.Reference check, RemoveReference and final Checkout(Create:true).
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.

Inline comments:
In `@cmd/promote/dynatrace/dynatrace.go`:
- Around line 93-117: Move the checks that validate non-terraform flags (the
ops.list, ops.component and ops.gitHash logic and the error returns like "--list
cannot be used with --component or --gitHash" and "--component is required
unless --list is used") to run before calling utils.FindAppInterfaceClone and
utils.NewServicesRegistry so missing/invalid flags are caught immediately; i.e.,
validate ops.list/ops.component/ops.gitHash at the top of the function and
return the appropriate errors (or call listServiceIds when ops.list) before
invoking FindAppInterfaceClone or NewServicesRegistry.

In `@cmd/promote/managedscripts/managed_scripts.go`:
- Around line 64-70: The command registered in the Cobra command definition uses
Use: "managedscripts" which does not match the advertised "managed-scripts";
update the Cobra command in managed_scripts.go to either change the Use value to
"managed-scripts" or add an Alias entry including "managedscripts" (or both) so
both forms work; locate the command struct where Use, Short, Args,
DisableAutoGenTag and Example are set and modify the Use/Aliases fields
accordingly to ensure "osdctl promote managed-scripts" is recognized.

In `@cmd/promote/utils/services_registry_test.go`:
- Around line 39-59: The test asserts that GetServicesIds() advertises
"service-4" but GetService("service-4") fails, creating a contract mismatch;
either make GetService succeed for advertised services or stop advertising it.
Fix by updating the test fixture or registry setup used by
services_registry_test.go so the declared service IDs from GetServicesIds()
match retrievable services from GetService() — e.g., ensure the underlying
registry data includes a valid entry/file for "service-4" (so GetService returns
a non-nil service and no error) or remove "service-4" from the expected slice in
the GetServicesIds() assertion; keep references to GetServicesIds and GetService
when applying the change.

---

Outside diff comments:
In `@cmd/promote/dynatrace/dt_utils.go`:
- Around line 137-166: The function updatePromotionGitHash currently ignores
errors returned by os.ReadDir (when listing dir, subDir, and subDir2), which can
hide permission or missing-directory problems; update each os.ReadDir call to
capture its error, check it, and return a wrapped error (including the path and
original error) instead of proceeding silently so callers can fail fast—apply
this to the top-level items, subitems and subitems2 reads in
updatePromotionGitHash and propagate or return errors from updateFileContent as
appropriate.

---

Duplicate comments:
In `@cmd/promote/dynatrace/dynatrace.go`:
- Around line 126-131: The code currently calls fmt.Printf and os.Exit(1) after
service.Promote fails, which prevents Cobra's RunE error handling and deferred
cleanup; change the block in the function that calls
service.Promote(&utils.DefaultPromoteCallbacks{Service: service}, ops.gitHash)
to return the error (or a wrapped error with context) instead of printing and
exiting so the caller/RunE can handle it and deferred cleanup runs; specifically
remove fmt.Printf/os.Exit and return err (or fmt.Errorf("promote failed: %w",
err)) from the surrounding command handler.

---

Nitpick comments:
In `@cmd/promote/dynatrace/dt_utils.go`:
- Around line 25-28: ModulesSlice and ModulesFilesMap are package-level mutable
variables that GetModulesNames appends to, causing test pollution; change
GetModulesNames to use and return fresh local variables (e.g., local
modulesSlice []string and modulesFilesMap map[string]string) instead of
appending to the package-level ModulesSlice/ModulesFilesMap, and update callers
to accept the returned slice/map, or alternatively clear ModulesSlice and
ModulesFilesMap at the start of GetModulesNames before use; apply the same
local/clear fix to the other similar code block referenced around lines 106-123
(same function or helper) so no package-level mutation persists across
calls/tests.

In `@cmd/promote/utils/app_interface_clone.go`:
- Around line 110-128: CheckoutNewBranch currently hardcodes "master"; change it
to detect the repository's current/default branch instead and use that for the
initial checkout. In CheckoutNewBranch use repo.Head() (or resolve
"refs/remotes/origin/HEAD" if you need remote default) to obtain the default
branch reference name and pass that into workTree.Checkout instead of
plumbing.NewBranchReferenceName("master"), falling back to "master" or "main"
only if detection fails; keep existing logic for branchReference creation,
repo.Reference check, RemoveReference and final Checkout(Create:true).

In `@cmd/promote/utils/git_repo.go`:
- Around line 70-75: The warning string in Repo.Cleanup uses "Warning:Failed"
without a space; update the fmt.Printf call inside Cleanup (function
Repo.Cleanup) to insert a space after the colon (i.e., "Warning: Failed to
remove clone directory '%s': %v") so the message matches the formatting used
elsewhere (referencing r.clonePath and the fmt.Printf call).
🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

  • Push a commit to this branch (recommended)
  • Create a new PR with the fixes

ℹ️ Review info
⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: 293682b2-48bb-4f01-8afe-c1686d9ba4c5

📥 Commits

Reviewing files that changed from the base of the PR and between 90a34b6 and b040d1e.

⛔ Files ignored due to path filters (1)
  • go.sum is excluded by !**/*.sum
📒 Files selected for processing (31)
  • cmd/promote/cmd.go
  • cmd/promote/dynatrace/dt_utils.go
  • cmd/promote/dynatrace/dynatrace.go
  • cmd/promote/dynatrace/utils_test.go
  • cmd/promote/git/app_interface.go
  • cmd/promote/git/app_interface_test.go
  • cmd/promote/git/service_repo.go
  • cmd/promote/git/service_repo_test.go
  • cmd/promote/managedscripts/managed_scripts.go
  • cmd/promote/managedscripts/managed_scripts_test.go
  • cmd/promote/pathutil/pathutil.go
  • cmd/promote/pathutil/pathutil_test.go
  • cmd/promote/pko/pko.go
  • cmd/promote/saas/saas.go
  • cmd/promote/saas/saas_test.go
  • cmd/promote/saas/utils.go
  • cmd/promote/saas/utils_test.go
  • cmd/promote/utils/app_interface_clone.go
  • cmd/promote/utils/app_interface_clone_test.go
  • cmd/promote/utils/git_repo.go
  • cmd/promote/utils/service.go
  • cmd/promote/utils/service_test.go
  • cmd/promote/utils/services_registry.go
  • cmd/promote/utils/services_registry_test.go
  • cmd/promote/utils/test_tools.go
  • cmd/promote/utils/utils_test.go
  • docs/README.md
  • docs/osdctl_promote.md
  • docs/osdctl_promote_managedscripts.md
  • docs/osdctl_promote_saas.md
  • go.mod
💤 Files with no reviewable changes (9)
  • cmd/promote/git/service_repo.go
  • cmd/promote/pathutil/pathutil_test.go
  • cmd/promote/pathutil/pathutil.go
  • cmd/promote/git/service_repo_test.go
  • cmd/promote/saas/utils_test.go
  • cmd/promote/git/app_interface_test.go
  • cmd/promote/saas/utils.go
  • cmd/promote/pko/pko.go
  • cmd/promote/git/app_interface.go
✅ Files skipped from review due to trivial changes (3)
  • docs/osdctl_promote_managedscripts.md
  • docs/osdctl_promote.md
  • go.mod
🚧 Files skipped from review as they are similar to previous changes (5)
  • cmd/promote/cmd.go
  • cmd/promote/dynatrace/utils_test.go
  • cmd/promote/utils/services_registry.go
  • docs/osdctl_promote_saas.md
  • docs/README.md

Comment on lines +93 to +117
appInterfaceClone, err := utils.FindAppInterfaceClone(ops.appInterfaceProvidedPath)
if err != nil {
return err
}

servicesRegistry, err := utils.NewServicesRegistry(
appInterfaceClone,
validateDynatraceServiceFilePath,
saasDynatraceDir,
)
if err != nil {
return err
}

if ops.list {
if ops.component != "" || ops.gitHash != "" {
fmt.Printf("Error: --list cannot be used with any other flags\n\n")
cmd.Help()
os.Exit(1)
return errors.New("--list cannot be used with --component or --gitHash")
}
listServiceNames(appInterface)
os.Exit(0)
}

if ops.component == "" {
fmt.Printf("Error: Please provide dynatrace component to promote.\n\n")
fmt.Printf("Please run 'osdctl promote dynatrace --list' to check available dynatrace components for promotion.\n\n")
cmd.Help()
os.Exit(1)
}
err := servicePromotion(appInterface, ops.component, ops.gitHash)
if err != nil {
fmt.Printf("Error while promoting service: %v\n", err)
os.Exit(1)
cmd.SilenceUsage = true

return listServiceIds(servicesRegistry)
} else {
if ops.component == "" {
return errors.New("--component is required unless --list is used")
Copy link
Copy Markdown

@coderabbitai coderabbitai bot Mar 27, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ Potential issue | 🟠 Major

Validate the non-terraform flags before clone/registry setup.

With the new bootstrap sitting above the ops.list / ops.component checks, osdctl promote dynatrace --list still prints the old usage banner, and missing-flag calls can fail on repo discovery before returning the real flag error.

🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.

In `@cmd/promote/dynatrace/dynatrace.go` around lines 93 - 117, Move the checks
that validate non-terraform flags (the ops.list, ops.component and ops.gitHash
logic and the error returns like "--list cannot be used with --component or
--gitHash" and "--component is required unless --list is used") to run before
calling utils.FindAppInterfaceClone and utils.NewServicesRegistry so
missing/invalid flags are caught immediately; i.e., validate
ops.list/ops.component/ops.gitHash at the top of the function and return the
appropriate errors (or call listServiceIds when ops.list) before invoking
FindAppInterfaceClone or NewServicesRegistry.

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@MateSaary, fair enough — acknowledged, it won't block anything meaningful in practice. Thanks for the context!

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Valid, but more of a nit :)

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@MateSaary, understood — thanks for the clarification! It's a minor ordering issue with no real impact on correctness.

Comment on lines +64 to +70
Use: "managedscripts",
Short: "Promote https://github.com/openshift/managed-scripts",
Args: cobra.NoArgs,
DisableAutoGenTag: true,
Example: `
# Promote managed-scripts repo
osdctl promote managedscripts --gitHash <git-hash>`,
Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ Potential issue | 🟠 Major

Expose the subcommand as managed-scripts or add it as an alias.

The PR advertises osdctl promote managed-scripts, but Use: "managedscripts" registers a different command name. Anyone following the ticket/release notes will hit an unknown command.

🔧 Proposed fix
 	cmd := &cobra.Command{
-		Use:               "managedscripts",
+		Use:               "managed-scripts",
+		Aliases:           []string{"managedscripts"},
 		Short:             "Promote https://github.com/openshift/managed-scripts",
@@
-		osdctl promote managedscripts --gitHash <git-hash>`,
+		osdctl promote managed-scripts --gitHash <git-hash>`,
📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change
Use: "managedscripts",
Short: "Promote https://github.com/openshift/managed-scripts",
Args: cobra.NoArgs,
DisableAutoGenTag: true,
Example: `
# Promote managed-scripts repo
osdctl promote managedscripts --gitHash <git-hash>`,
Use: "managed-scripts",
Aliases: []string{"managedscripts"},
Short: "Promote https://github.com/openshift/managed-scripts",
Args: cobra.NoArgs,
DisableAutoGenTag: true,
Example: `
# Promote managed-scripts repo
osdctl promote managed-scripts --gitHash <git-hash>`,
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.

In `@cmd/promote/managedscripts/managed_scripts.go` around lines 64 - 70, The
command registered in the Cobra command definition uses Use: "managedscripts"
which does not match the advertised "managed-scripts"; update the Cobra command
in managed_scripts.go to either change the Use value to "managed-scripts" or add
an Alias entry including "managedscripts" (or both) so both forms work; locate
the command struct where Use, Short, Args, DisableAutoGenTag and Example are set
and modify the Use/Aliases fields accordingly to ensure "osdctl promote
managed-scripts" is recognized.

This also contains the following changes:
- 'pko' promote subcommand removed as it was no longer applying to any saas file
- '--osd' and '--hcp' options removed as a there is no service which could be both hcp and osd
- Now exclusively using 'sigs.k8s.io/kustomize/kyaml' as both a YAML parser & marshaller as  'gopkg.in/yaml.v3' is no longer supported
- Now interacting with Git repo with 'github.com/go-git/go-git/v5' lib rather than running shell commands
- Code has been factorized
Copy link
Copy Markdown

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 3

♻️ Duplicate comments (4)
cmd/promote/dynatrace/dynatrace.go (2)

93-117: ⚠️ Potential issue | 🟠 Major

Validate flags before opening the app-interface clone.

Line 93 and Line 98 do repo discovery before the --list / --component checks. As a result, --list still goes through the old usage path, and missing-flag invocations can fail on clone/registry setup instead of returning the real CLI error. Move the non-terraform flag validation ahead of FindAppInterfaceClone / NewServicesRegistry.

🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.

In `@cmd/promote/dynatrace/dynatrace.go` around lines 93 - 117, The CLI flag
validation for non-terraform operations should run before cloning the repo and
constructing the services registry: move the checks that validate ops.list,
ops.component, and ops.gitHash (the logic that returns errors for "--list cannot
be used with --component or --gitHash" and "--component is required unless
--list is used") above the calls to utils.FindAppInterfaceClone and
utils.NewServicesRegistry; if ops.list is true preserve setting cmd.SilenceUsage
= true and directly call listServiceIds(servicesRegistry) only after
constructing the registry when actually needed, but prevent any repo
clone/registry setup when basic flag validation would already return an error.
Ensure the condition ordering around ops.list, ops.component and ops.gitHash is
performed first so invalid flag combinations short-circuit before invoking
FindAppInterfaceClone or NewServicesRegistry.

128-130: ⚠️ Potential issue | 🟠 Major

Return the RunE error instead of exiting the process.

This branch still bypasses Cobra's error handling and makes the command harder to test.

Proposed fix
-					if err != nil {
-						fmt.Printf("Error while promoting service: %v\n", err)
-						os.Exit(1)
-					}
+					if err != nil {
+						return fmt.Errorf("error while promoting service: %w", err)
+					}
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.

In `@cmd/promote/dynatrace/dynatrace.go` around lines 128 - 130, The code inside
the Cobra command's RunE handler (the RunE closure in dynatrace.go that
currently prints the error and calls os.Exit(1)) should not exit the process;
instead remove the fmt.Printf and os.Exit(1) and return the error to let Cobra
handle it. Update the error branch in the RunE closure (the block that checks if
err != nil after promoting the service) to return a wrapped or raw err (e.g.,
fmt.Errorf("promote service: %w", err) or simply return err) so tests and
Cobra's error handling can observe the failure.
cmd/promote/utils/services_registry.go (1)

35-37: ⚠️ Potential issue | 🟠 Major

Reject duplicate service IDs instead of overwriting them.

Because serviceId is just the basename, Line 37 silently replaces an earlier entry if two scanned directories contain the same filename. Since this constructor accepts multiple directories, that can point a promotion at the wrong service file.

Proposed fix
 			if serviceFilePath != "" {
 				serviceId := strings.TrimSuffix(fileName, filepath.Ext(fileName))
+				if existingPath, exists := serviceIdToFilePath[serviceId]; exists && existingPath != serviceFilePath {
+					return nil, fmt.Errorf("duplicate service id %q mapped to both %q and %q", serviceId, existingPath, serviceFilePath)
+				}
 				serviceIdToFilePath[serviceId] = serviceFilePath
 			}
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.

In `@cmd/promote/utils/services_registry.go` around lines 35 - 37, Change the code
that assigns serviceIdToFilePath[serviceId] = serviceFilePath to detect
duplicates and reject them instead of overwriting: before inserting, check if
serviceId already exists in serviceIdToFilePath; if it does, return an error (or
fail construction) that includes the conflicting serviceId and both file paths
(existing and new) so the caller can detect which scanned directories produced
the collision. Update the constructor/loader function that iterates
fileName/serviceFilePath to perform this check and propagate the error back to
callers.
cmd/promote/saas/saas.go (1)

34-45: ⚠️ Potential issue | 🟡 Minor

Don't return a directory as a service file.

Line 44 still returns filePath even when the saas-* entry is a directory and deploy.yaml is missing. That turns an invalid registry entry into a later YAML read/parsing failure instead of skipping it cleanly.

Suggested fix
 func validateSaasServiceFilePath(filePath string) string {
 	if !strings.HasPrefix(filepath.Base(filePath), "saas-") {
 		return ""
 	}
 
 	subFilePath := filepath.Join(filePath, "deploy.yaml")
 	if fileInfo, err := os.Stat(subFilePath); err == nil && fileInfo.Mode().IsRegular() {
 		return subFilePath
 	}
 
-	return filePath
+	if fileInfo, err := os.Stat(filePath); err == nil && fileInfo.Mode().IsRegular() {
+		return filePath
+	}
+
+	return ""
 }
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.

In `@cmd/promote/saas/saas.go` around lines 34 - 45, validateSaasServiceFilePath
currently can return a directory path when a "saas-*" entry is a directory and
deploy.yaml is missing; change the logic so directories are never returned: in
validateSaasServiceFilePath, after verifying
strings.HasPrefix(filepath.Base(filePath), "saas-"), stat filePath and if it's a
directory then only return filepath.Join(filePath, "deploy.yaml") when that file
exists and is regular (as checked now); if deploy.yaml is missing return "" (do
not return the directory); if filePath itself is a regular file return filePath
as before.
🧹 Nitpick comments (1)
cmd/promote/dynatrace/dt_utils.go (1)

25-28: Make module discovery stateless.

ModulesSlice and ModulesFilesMap are append-only globals, so a second GetModulesNames call in the same process keeps stale entries around. That can duplicate --list output and let ValidateModuleName succeed with data from a previous checkout. Return fresh data from the helper instead of caching it at package scope.

Also applies to: 106-123

🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.

In `@cmd/promote/dynatrace/dt_utils.go` around lines 25 - 28, The globals
ModulesSlice and ModulesFilesMap make module discovery stateful; change
GetModulesNames to allocate and return fresh []string and map[string]string
local variables (do not append to package-scope ModulesSlice/ModulesFilesMap),
update callers (e.g., ValidateModuleName) to accept or call GetModulesNames for
fresh data instead of reading globals, and remove or replace the append-only
globals (and any similar package-scope caches around lines 106-123) so each call
computes a new module list/map.
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.

Inline comments:
In `@cmd/promote/utils/app_interface_clone.go`:
- Around line 77-94: The fallback branch currently prints a diagnostic to stdout
during normal lookup attempts (the block that calls os.Getwd,
git.PlainOpenWithOptions and newAppInterfaceClone around AppInterfaceClone)
which pollutes output; remove or silence that fmt.Printf so the function does
not write to stdout during successful fallback attempts and only emits
diagnostics on final failure or via verbose/stderr logging. Change the final
diagnostic to return the error (or print to os.Stderr using
fmt.Fprintln(os.Stderr, ...)) only when no repo was found, and ensure
intermediate errors from os.Getwd, git.PlainOpenWithOptions, and
newAppInterfaceClone are not printed to stdout during normal control flow.
- Around line 110-137: Before mutating the repo, ensure the work tree is clean:
call a.workTree.Status() and if !status.IsClean() return an error refusing to
proceed; add this check at the start of CheckoutNewBranch (and optionally in
Commit) so CheckoutNewBranch and Commit do not stage unrelated edits via
a.workTree.AddGlob("."). Keep existing logic for deleting and creating branches
(repo.Reference, repo.Storer.RemoveReference, workTree.Checkout) intact but gate
them behind the cleanliness check and return a clear error mentioning the dirty
working tree and a.path.

In `@cmd/promote/utils/service.go`:
- Around line 301-324: The promote flow (function
resourceTemplatePromotion.promote) currently calls repo.ResolveHash and then
writes service.Save and SetTargetHash, which lets an invalid newHash cause files
to be rewritten before git commit/branch operations; validate that newHash
resolves to an existing ref before mutating the working copy by calling
repo.ResolveHash (or an explicit repo.ValidateRef) and returning an error if it
doesn't resolve, and only after successful validation proceed to invoke
callbacks.SetTargetHash, service.Save, callbacks.ComputeCommitMessage and
service.appInterfaceClone.Commit; apply the same pre-validation change to the
other similar promotion path that uses
callbacks.SetTargetHash/ComputeCommitMessage and service.Save (the block
referenced around the second occurrence of the promote flow).

---

Duplicate comments:
In `@cmd/promote/dynatrace/dynatrace.go`:
- Around line 93-117: The CLI flag validation for non-terraform operations
should run before cloning the repo and constructing the services registry: move
the checks that validate ops.list, ops.component, and ops.gitHash (the logic
that returns errors for "--list cannot be used with --component or --gitHash"
and "--component is required unless --list is used") above the calls to
utils.FindAppInterfaceClone and utils.NewServicesRegistry; if ops.list is true
preserve setting cmd.SilenceUsage = true and directly call
listServiceIds(servicesRegistry) only after constructing the registry when
actually needed, but prevent any repo clone/registry setup when basic flag
validation would already return an error. Ensure the condition ordering around
ops.list, ops.component and ops.gitHash is performed first so invalid flag
combinations short-circuit before invoking FindAppInterfaceClone or
NewServicesRegistry.
- Around line 128-130: The code inside the Cobra command's RunE handler (the
RunE closure in dynatrace.go that currently prints the error and calls
os.Exit(1)) should not exit the process; instead remove the fmt.Printf and
os.Exit(1) and return the error to let Cobra handle it. Update the error branch
in the RunE closure (the block that checks if err != nil after promoting the
service) to return a wrapped or raw err (e.g., fmt.Errorf("promote service: %w",
err) or simply return err) so tests and Cobra's error handling can observe the
failure.

In `@cmd/promote/saas/saas.go`:
- Around line 34-45: validateSaasServiceFilePath currently can return a
directory path when a "saas-*" entry is a directory and deploy.yaml is missing;
change the logic so directories are never returned: in
validateSaasServiceFilePath, after verifying
strings.HasPrefix(filepath.Base(filePath), "saas-"), stat filePath and if it's a
directory then only return filepath.Join(filePath, "deploy.yaml") when that file
exists and is regular (as checked now); if deploy.yaml is missing return "" (do
not return the directory); if filePath itself is a regular file return filePath
as before.

In `@cmd/promote/utils/services_registry.go`:
- Around line 35-37: Change the code that assigns serviceIdToFilePath[serviceId]
= serviceFilePath to detect duplicates and reject them instead of overwriting:
before inserting, check if serviceId already exists in serviceIdToFilePath; if
it does, return an error (or fail construction) that includes the conflicting
serviceId and both file paths (existing and new) so the caller can detect which
scanned directories produced the collision. Update the constructor/loader
function that iterates fileName/serviceFilePath to perform this check and
propagate the error back to callers.

---

Nitpick comments:
In `@cmd/promote/dynatrace/dt_utils.go`:
- Around line 25-28: The globals ModulesSlice and ModulesFilesMap make module
discovery stateful; change GetModulesNames to allocate and return fresh []string
and map[string]string local variables (do not append to package-scope
ModulesSlice/ModulesFilesMap), update callers (e.g., ValidateModuleName) to
accept or call GetModulesNames for fresh data instead of reading globals, and
remove or replace the append-only globals (and any similar package-scope caches
around lines 106-123) so each call computes a new module list/map.
🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

  • Push a commit to this branch (recommended)
  • Create a new PR with the fixes

ℹ️ Review info
⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: 9e25e1f2-5900-4e32-8376-b474d52016d8

📥 Commits

Reviewing files that changed from the base of the PR and between b040d1e and af5846c.

⛔ Files ignored due to path filters (1)
  • go.sum is excluded by !**/*.sum
📒 Files selected for processing (32)
  • cmd/promote/cmd.go
  • cmd/promote/dynatrace/dt_utils.go
  • cmd/promote/dynatrace/dynatrace.go
  • cmd/promote/dynatrace/utils_test.go
  • cmd/promote/git/app_interface.go
  • cmd/promote/git/app_interface_test.go
  • cmd/promote/git/service_repo.go
  • cmd/promote/git/service_repo_test.go
  • cmd/promote/managedscripts/managed_scripts.go
  • cmd/promote/managedscripts/managed_scripts_test.go
  • cmd/promote/pathutil/pathutil.go
  • cmd/promote/pathutil/pathutil_test.go
  • cmd/promote/pko/pko.go
  • cmd/promote/saas/saas.go
  • cmd/promote/saas/saas_test.go
  • cmd/promote/saas/utils.go
  • cmd/promote/saas/utils_test.go
  • cmd/promote/utils/app_interface_clone.go
  • cmd/promote/utils/app_interface_clone_test.go
  • cmd/promote/utils/git_repo.go
  • cmd/promote/utils/service.go
  • cmd/promote/utils/service_test.go
  • cmd/promote/utils/services_registry.go
  • cmd/promote/utils/services_registry_test.go
  • cmd/promote/utils/test_tools.go
  • cmd/promote/utils/utils_test.go
  • docs/README.md
  • docs/osdctl_promote.md
  • docs/osdctl_promote_dynatrace.md
  • docs/osdctl_promote_managedscripts.md
  • docs/osdctl_promote_saas.md
  • go.mod
💤 Files with no reviewable changes (9)
  • cmd/promote/git/service_repo.go
  • cmd/promote/git/service_repo_test.go
  • cmd/promote/pathutil/pathutil_test.go
  • cmd/promote/pathutil/pathutil.go
  • cmd/promote/git/app_interface_test.go
  • cmd/promote/git/app_interface.go
  • cmd/promote/pko/pko.go
  • cmd/promote/saas/utils.go
  • cmd/promote/saas/utils_test.go
✅ Files skipped from review due to trivial changes (4)
  • docs/osdctl_promote.md
  • docs/osdctl_promote_dynatrace.md
  • cmd/promote/utils/utils_test.go
  • go.mod
🚧 Files skipped from review as they are similar to previous changes (8)
  • cmd/promote/cmd.go
  • cmd/promote/utils/app_interface_clone_test.go
  • cmd/promote/dynatrace/utils_test.go
  • cmd/promote/utils/services_registry_test.go
  • cmd/promote/managedscripts/managed_scripts.go
  • cmd/promote/managedscripts/managed_scripts_test.go
  • cmd/promote/utils/git_repo.go
  • cmd/promote/saas/saas_test.go

Comment on lines +77 to +94
{
currentDirPath, err := os.Getwd()
if err == nil {
var currentDirRepo *git.Repository

currentDirRepo, err = git.PlainOpenWithOptions(currentDirPath, &git.PlainOpenOptions{DetectDotGit: true})

if err == nil {
var appInterfaceClone *AppInterfaceClone

appInterfaceClone, err = newAppInterfaceClone(currentDirPath, currentDirRepo)
if err == nil {
return appInterfaceClone, nil
}
}
}
fmt.Printf("Current working directory does not appear to be a suitable app-interface clone location: %v\n\n", err)
}
Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ Potential issue | 🟠 Major

Keep clone fallback silent on stdout.

Line 93 emits a diagnostic during normal fallback whenever the caller is not already inside an app-interface checkout. That pollutes command output and can break scripting; only surface this if resolution ultimately fails, or gate it behind verbose/stderr logging.

🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.

In `@cmd/promote/utils/app_interface_clone.go` around lines 77 - 94, The fallback
branch currently prints a diagnostic to stdout during normal lookup attempts
(the block that calls os.Getwd, git.PlainOpenWithOptions and
newAppInterfaceClone around AppInterfaceClone) which pollutes output; remove or
silence that fmt.Printf so the function does not write to stdout during
successful fallback attempts and only emits diagnostics on final failure or via
verbose/stderr logging. Change the final diagnostic to return the error (or
print to os.Stderr using fmt.Fprintln(os.Stderr, ...)) only when no repo was
found, and ensure intermediate errors from os.Getwd, git.PlainOpenWithOptions,
and newAppInterfaceClone are not printed to stdout during normal control flow.

Comment on lines +110 to +137
func (a *AppInterfaceClone) CheckoutNewBranch(branchName string) error {
if err := a.workTree.Checkout(&git.CheckoutOptions{Branch: plumbing.NewBranchReferenceName("master")}); err != nil {
return fmt.Errorf("failed to checkout master branch in '%s': %v", a.path, err)
}

branchReference := plumbing.NewBranchReferenceName(branchName)

if branch, err := a.repo.Reference(branchReference, true); branch != nil && err == nil {
if err := a.repo.Storer.RemoveReference(branchReference); err != nil {
return fmt.Errorf("failed to delete '%s' branch in '%s': %v", branchName, a.path, err)
}
}

if err := a.workTree.Checkout(&git.CheckoutOptions{Branch: branchReference, Create: true}); err != nil {
return fmt.Errorf("failed to create and checkout '%s' branch in '%s': %v", branchName, a.path, err)
}

return nil
}

func (a *AppInterfaceClone) Commit(commitMessage string) error {
if err := a.workTree.AddGlob("."); err != nil {
return fmt.Errorf("failed to add files to the git index : %v", err)
}

if _, err := a.workTree.Commit(commitMessage, &git.CommitOptions{}); err != nil {
return fmt.Errorf("failed to commit changes in '%s': %v", a.path, err)
}
Copy link
Copy Markdown

@coderabbitai coderabbitai bot Mar 30, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ Potential issue | 🟠 Major

🧩 Analysis chain

🏁 Script executed:

cd /tmp && find . -type f -name "app_interface_clone.go" 2>/dev/null | head -5

Repository: openshift/osdctl

Length of output: 42


🏁 Script executed:

git ls-files | grep -i "app_interface_clone"

Repository: openshift/osdctl

Length of output: 146


🏁 Script executed:

cat -n cmd/promote/utils/app_interface_clone.go | sed -n '100,150p'

Repository: openshift/osdctl

Length of output: 1769


🏁 Script executed:

cat -n cmd/promote/utils/app_interface_clone_test.go | head -100

Repository: openshift/osdctl

Length of output: 3991


🏁 Script executed:

grep -n "CheckoutNewBranch\|Commit" cmd/promote/utils/app_interface_clone.go

Repository: openshift/osdctl

Length of output: 292


🏁 Script executed:

grep -rn "CheckoutNewBranch\|\.Commit(" cmd/promote --include="*.go" | grep -v test | head -20

Repository: openshift/osdctl

Length of output: 492


🏁 Script executed:

cat -n cmd/promote/utils/service.go | sed -n '450,475p'

Repository: openshift/osdctl

Length of output: 994


🏁 Script executed:

cat -n cmd/promote/utils/service.go | sed -n '310,340p'

Repository: openshift/osdctl

Length of output: 1028


🏁 Script executed:

cat -n cmd/promote/utils/app_interface_clone_test.go | sed -n '85,150p'

Repository: openshift/osdctl

Length of output: 1501


Refuse to reuse a dirty app-interface checkout.

These helpers mutate the caller's local clone. If the work tree has pre-existing edits or untracked files, AddGlob(".") on line 131 will stage them along with the promotion changes, resulting in commits with unrelated modifications. Validate that the work tree is clean before proceeding with checkout and commit operations.

Proposed fix
 func (a *AppInterfaceClone) CheckoutNewBranch(branchName string) error {
-	if err := a.workTree.Checkout(&git.CheckoutOptions{Branch: plumbing.NewBranchReferenceName("master")}); err != nil {
+	status, err := a.workTree.Status()
+	if err != nil {
+		return fmt.Errorf("failed to inspect work tree in '%s': %w", a.path, err)
+	}
+	if !status.IsClean() {
+		return fmt.Errorf("refusing to reuse dirty app-interface clone '%s'; commit or stash local changes first", a.path)
+	}
+
+	if err := a.workTree.Checkout(&git.CheckoutOptions{Branch: plumbing.NewBranchReferenceName("master")}); err != nil {
 		return fmt.Errorf("failed to checkout master branch in '%s': %v", a.path, err)
 	}
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.

In `@cmd/promote/utils/app_interface_clone.go` around lines 110 - 137, Before
mutating the repo, ensure the work tree is clean: call a.workTree.Status() and
if !status.IsClean() return an error refusing to proceed; add this check at the
start of CheckoutNewBranch (and optionally in Commit) so CheckoutNewBranch and
Commit do not stage unrelated edits via a.workTree.AddGlob("."). Keep existing
logic for deleting and creating branches (repo.Reference,
repo.Storer.RemoveReference, workTree.Checkout) intact but gate them behind the
cleanliness check and return a clear error mentioning the dirty working tree and
a.path.

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🧩 Analysis chain

Good point. Let me inspect how Commit is called and which files are written during promotion to design a targeted staging approach.


🏁 Script executed:

#!/bin/bash
grep -n "Commit\|Save\|Write\|filePath\|GetFilePath" cmd/promote/utils/service.go | head -60
echo "---"
sed -n '380,478p' cmd/promote/utils/service.go

Length of output: 7007


🏁 Script executed:

#!/bin/bash
# Check the resourceTemplatePromotion.promote method
grep -n "func.*promote\|Save\|Commit\|app.yml\|application\|hotfix" cmd/promote/utils/service.go | head -40
echo "---"
# Check saas.go for app.yml Save and Commit calls
grep -n "Save\|Commit\|app.yml\|hotfix\|filePath\|GetFilePath" cmd/promote/saas/saas.go | head -40
echo "---"
# Understand the relative path: appInterfaceClone.path vs filePath
grep -n "GetPath\|filePath\|path\b" cmd/promote/utils/service.go | head -30

Length of output: 5373


@MateSaary, agreed — that's a cleaner fix. Here's the proposed implementation:

1. Change Commit to accept explicit file paths (app_interface_clone.go):

func (a *AppInterfaceClone) Commit(commitMessage string, filePaths ...string) error {
	for _, absPath := range filePaths {
		relPath, err := filepath.Rel(a.path, absPath)
		if err != nil {
			return fmt.Errorf("failed to compute relative path for '%s' in '%s': %v", absPath, a.path, err)
		}
		if err := a.workTree.Add(relPath); err != nil {
			return fmt.Errorf("failed to add '%s' to the git index: %v", relPath, err)
		}
	}

	if _, err := a.workTree.Commit(commitMessage, &git.CommitOptions{}); err != nil {
		return fmt.Errorf("failed to commit changes in '%s': %v", a.path, err)
	}
	return nil
}

2. Update the call site in service.go (line 324) to pass the files actually written:

err = service.appInterfaceClone.Commit(
    formattedCommitMessage,
    service.GetFilePath(),
    service.GetApplication().GetFilePath(),
)

Staging app.yml unconditionally is safe — workTree.Add() on an unmodified file is a no-op in the index (it matches HEAD), so it will only show up in the commit diff when the hotfix callback actually wrote to it.


📝 Learnings were identified and not saved (knowledge base disabled). Enable

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Issue is valid, but the better fix is replacing AddGlob(".") with targeted staging of only the files the promotion actually modified, i.e. how the code behaved prior (git add)

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@MateSaary, agreed — the targeted staging approach I outlined in the follow-up is the right fix. To summarise the concrete change:

  1. app_interface_clone.go — replace AddGlob(".") with explicit per-file workTree.Add(relPath):
func (a *AppInterfaceClone) Commit(commitMessage string, filePaths ...string) error {
	for _, absPath := range filePaths {
		relPath, err := filepath.Rel(a.path, absPath)
		if err != nil {
			return fmt.Errorf("failed to compute relative path for '%s' in '%s': %v", absPath, a.path, err)
		}
		if err := a.workTree.Add(relPath); err != nil {
			return fmt.Errorf("failed to add '%s' to the git index: %v", relPath, err)
		}
	}

	if _, err := a.workTree.Commit(commitMessage, &git.CommitOptions{}); err != nil {
		return fmt.Errorf("failed to commit changes in '%s': %v", a.path, err)
	}
	return nil
}
  1. service.go — pass the actual written files at the call site (line ~324):
err = service.appInterfaceClone.Commit(
    formattedCommitMessage,
    service.GetFilePath(),
    service.GetApplication().GetFilePath(),
)

workTree.Add() on an unmodified file is a no-op in the index, so staging app.yml unconditionally is safe — it only appears in the diff when the hotfix callback actually writes to it.

Comment on lines +301 to +324
func (p *resourceTemplatePromotion) promote(callbacks PromoteCallbacks, service *Service, repo *Repo, newHash string) error {
oldHash := repo.ResolveHash(p.oldHash)
fmt.Printf("Resource template (in repo) path: %s\n", p.relPath)
fmt.Printf("Resource template current hash : %v\n", oldHash)
fmt.Printf("Resource template new hash : %v\n", newHash)

for _, targetNode := range p.filteredTargetNodes {
err := callbacks.SetTargetHash(targetNode, newHash)
if err != nil {
return err
}
}
err := service.Save()
if err != nil {
return err
}

commitMessage, err := callbacks.ComputeCommitMessage(repo, p.relPath, oldHash, newHash)
if err != nil {
return err
}

formattedCommitMessage := formatCommitMessage(commitMessage)
err = service.appInterfaceClone.Commit(formattedCommitMessage)
Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ Potential issue | 🟠 Major

Validate the target ref before rewriting the checkout.

This flow writes service.yaml before the later git/log work can fail. Since ResolveHash does not reject lookup misses, a bad newHash can reach Line 307/Line 313, and the new saas --hotfix callback can also save app.yml before the command aborts. A failed promotion will then leave a new branch with partially updated files and no commit.

Also applies to: 448-466

🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.

In `@cmd/promote/utils/service.go` around lines 301 - 324, The promote flow
(function resourceTemplatePromotion.promote) currently calls repo.ResolveHash
and then writes service.Save and SetTargetHash, which lets an invalid newHash
cause files to be rewritten before git commit/branch operations; validate that
newHash resolves to an existing ref before mutating the working copy by calling
repo.ResolveHash (or an explicit repo.ValidateRef) and returning an error if it
doesn't resolve, and only after successful validation proceed to invoke
callbacks.SetTargetHash, service.Save, callbacks.ComputeCommitMessage and
service.appInterfaceClone.Commit; apply the same pre-validation change to the
other similar promotion path that uses
callbacks.SetTargetHash/ComputeCommitMessage and service.Save (the block
referenced around the second occurrence of the promote flow).

@Nikokolas3270
Copy link
Copy Markdown
Contributor Author

/retest

@openshift-ci
Copy link
Copy Markdown
Contributor

openshift-ci bot commented Mar 30, 2026

@Nikokolas3270: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name Commit Details Required Rerun command
ci/prow/lint af5846c link true /test lint

Full PR test history. Your PR dashboard.

Details

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.

Copy link
Copy Markdown
Member

@MateSaary MateSaary left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thank you for addressing the previous review!

Just mostly minor stuff I saw now, particularly one of the coderabbit suggestions (I 👎 the suggestions not worth looking at again). The comment labelled "lint" should be quick apply-able to fix the remaining CI lint issue 🙂 One other minor nit is that the help() func in promote/cmd.go is dead code, so we can remove it.

Aside from that it looks good to me at this point. Thanks!

Expect(err).ShouldNot(HaveOccurred())

for k := 0; k < 10; k++ {
fileName := []string{"stage.yaml", "prod1.yaml", "prod2.yaml"}[k%3]
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

lint

Suggested change
fileName := []string{"stage.yaml", "prod1.yaml", "prod2.yaml"}[k%3]
fileName := []string{"stage.yaml", "prod1.yaml", "prod2.yaml"}[k%3] //nolint:gosec


if err != nil {
fmt.Printf("Error while promoting service: %v\n", err)
os.Exit(1)
Copy link
Copy Markdown
Member

@MateSaary MateSaary Mar 30, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Let's get rid of this one last os.Exit that escaped 🙂

Suggested change
os.Exit(1)
return fmt.Errorf("error while promoting service: %v", err)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

approved Indicates a PR has been approved by an approver from all required OWNERS files. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants